Browsing {json:api} documents as a human
TLDR: I wrote a tool to visualise {json:api} documents
There are good and bad things about {json:api}. For example, their website covers most of what you’ll need and is well illustrated with examples. Yet if you need anything else it’s hard to find it because of its generic name: search results always yield false-positives.
Another great thing about {json:api} is its serialisation format. A quote from their website:
JSON API flattens the entire graph of objects at the top level. This means that if the same “people” are referenced from different kinds of objects (say, the author of both posts and comments), this format ensures that there is only a single representation of each person document in the payload.
This is great for machines but is not as intuitive for humans as, say, recursively nesting child entities to express a relationship. Even though most of the humans looking at a...